Skip to main content

This is a new service – your feedback will help us to improve it.

Leeds City Council

Tree preservation zone

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order dataset

A1

reference
TPO2014_012_A_001
name
A1
tree-preservation-order

undefined

TPO2014_012
tree-preservation-zone-type
area
geometry
MULTIPOLYGON (((-1.629138 53.775531,-1.629202 53.775566,-1.629025 53.775854,-1.628959 53.775914,-1.629024 53.775967,-1.629090 53.775981,-1.629161 53.775940,-1.629431 53.775679,-1.629773 53.775287,-1.630075 53.774782,-1.630512 53.773931,-1.630372 53.773906,-1.630418 53.773849,-1.630173 53.773794,-1.630274 53.773488,-1.630535 53.773485,-1.630680 53.773375,-1.630802 53.773406,-1.630851 53.773346,-1.630491 53.773241,-1.630675 53.772932,-1.630589 53.772906,-1.630805 53.772611,-1.630021 53.772520,-1.630018 53.772537,-1.629259 53.772775,-1.629115 53.772452,-1.629039 53.772321,-1.628974 53.772156,-1.628816 53.772230,-1.628711 53.772262,-1.628549 53.772285,-1.628038 53.772327,-1.628044 53.772353,-1.628803 53.772277,-1.628923 53.772579,-1.628521 53.772676,-1.627691 53.772932,-1.627493 53.772990,-1.627492 53.772984,-1.627052 53.773118,-1.627085 53.773175,-1.626991 53.773201,-1.626953 53.773148,-1.626796 53.773194,-1.626787 53.773209,-1.626769 53.773210,-1.626901 53.773360,-1.626994 53.773500,-1.627123 53.773650,-1.627198 53.773758,-1.627566 53.774366,-1.627605 53.774440,-1.627671 53.774614,-1.627705 53.774677,-1.627754 53.774647,-1.627827 53.774692,-1.627801 53.774708,-1.629138 53.775531)))
point
POINT (-1.628953 53.773861)
notes
entry-date
2026-02-12
start-date
2014-07-03
end-date

How to fix this issue

Your dataset is missing the tree-preservation-order column.

The Tree preservation zone guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that covers this zone.

How to improve Leeds City Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL